Release Notes - 06 February 2023 Updates
Explore the new features added in this update!
Updated on: 06 February 2023
Release Version: 0.11
| Feature | Description |
|---|---|
| Ability to view and edit configuration for custom transformation jobs | In Lazsa Data Pipeline Studio, you can now view and edit the configuration of a custom transformation job. |
| Versioning and rollback of data pipelines | In Lazsa Data Pipeline Studio, you can create versions for data pipelines and roll back to a required version. You can also promote the data pipeline to the various stages for testing. |
| Multiple response formats supported for REST API jobs | The REST API jobs now support CSV as a response format along with JSON. |
| Save SQL queries to source code repo and view history of query runs for custom transformation jobs | Lazsa Data Pipeline Studio now provides the ability to save SQL queries for custom transformation jobs to a configured source code repository. You can view the query runs using the View History option. |
| Stoplist and Healthcheck for filtering files being pushed to S3 Data Lake. | Before pushing your files to an S3 Data Lake, you can use the Stoplist and Healthcheck features for filtering tar.gz and .gz files that are corrupt or are not to be processed. |
| Upgrade and downgrade of wheel package | Lazsa Data Pipeline Studio now provides the Manage Wheel Package option to upgrade or downgrade the wheel package being used for running a Databricks job. The option is available on (…) of the home page of Data Pipeline Studio. |
| AWS Glue DataBrew jobs for data quality | Lazsa Data Pipeline Studio now provides the ability to use AWS Glue DataBrew for data quality in a data pipeline. |
| Lazsa Action to invoke external API endpoint | You can use Lazsa Action in the Data Transformation stage to invoke an external API endpoint. |
| Support for AWS Glue Integration | Lazsa Data Pipeline Studio now supports AWS Glue in the Data Integration layer for sources like RDBMS or REST API to Data Lake as Amazon S3. |
| Bitbucket Server configuration enhancement | To connect to your Bitbucket Server admin account from within the Lazsa platform, now you need to configure the API token in addition to username and password. If the Bitbucket Server password that you have configured in the Lazsa platform expires, you can still connect to your account by using the API token. |
| New version of Lazsa Orchestrator Agent available | The Lazsa Orchestrator Agent is updated to a new version. On the Lazsa Orchestrator Agents screen, click Update Available for instructions to upgrade the agent to the latest available version. See Lazsa Orchestrator Agent. |